chore(deps): bump next from 16.2.3 to 16.2.6#100
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [next](https://github.com/vercel/next.js) from 16.2.3 to 16.2.6. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v16.2.3...v16.2.6) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps next from 16.2.3 to 16.2.6.
Release notes
Sourced from next's releases.
... (truncated)
Commits
ee6e79bv16.2.6afa053dTurbopack: Match proxy matchers with webpack implementation (#93594)97a154eTurbopack: Fix middleware matcher suffix (#93590)83899bc[backport] Disable build caches for production/staging/force-preview deploys ...7b222b9[backport][test] Pin package manager to patch versions (#93595)a8dc24f[backport] Turbopack: more strict vergen setup (#93587)766148fv16.2.50dd9483fix: add explicit checks for RSC header (#83) (#98)d166096fix proxy matching for segment prefetch URLs (#89) (#96)9d50c0bStrip next-resume header from incoming requests (#92)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Greptile Summary
This PR bumps
nextfrom16.2.3to16.2.6across all three workspaces (apps/docs,apps/examples/nextjs-example,packages/nextjs) to address a large batch of security advisories fixed in16.2.5and16.2.6.pnpm-lock.yamlis updated consistently — all resolved references tonext@16.2.3have been replaced withnext@16.2.6across every workspace, with no unexpected dependency additions.Confidence Score: 5/5
Safe to merge — this is a patch-level dependency bump that exclusively addresses published security advisories with no API or behavioral changes for application code.
All three package.json files receive the same mechanical version bump, the lockfile resolves consistently to next@16.2.6 everywhere, and the change ships no new code of its own. The upgrade resolves 13 published CVEs and is a straightforward security maintenance update.
No files require special attention. The lockfile update is large but routine — all next@16.2.3 resolutions have been uniformly replaced with next@16.2.6.
Important Files Changed
nextpeer dependency from^16.2.3to^16.2.6— security patch update only, no other changes.nextfrom^16.2.3to^16.2.6— security patch update only, no other changes.nextdev dependency from^16.2.3to^16.2.6— security patch update only, no other changes.next@16.2.6across all three workspaces; all peer dependency resolutions updated consistently.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[dependabot PR] --> B[Bump next 16.2.3 → 16.2.6] B --> C[apps/docs/package.json] B --> D[apps/examples/nextjs-example/package.json] B --> E[packages/nextjs/package.json] C & D & E --> F[pnpm-lock.yaml updated] F --> G{Security fixes applied} G --> H[7 High advisories resolved] G --> I[4 Moderate advisories resolved] G --> J[2 Low advisories resolved]Reviews (1): Last reviewed commit: "chore(deps): bump next from 16.2.3 to 16..." | Re-trigger Greptile